ESLint: Update rules #107
Merged
ESLint: Update rules #107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juanchoperezj
requested review from
asdolo,
fernandatoledo,
guillermomachado and
marcos09
💯 Test Coverage
😎 Tests Results
👀 Tests Details • (54%)
|
asdolo
approved these changes
Dec 12, 2024
guillermomachado
approved these changes
Dec 18, 2024
Stukz
approved these changes
Dec 23, 2024
guillermomachado
force-pushed
the
feature/eslint-new-rules
branch
from
fdd6d3b to
9757074
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do?
Add new linting rules.
Why did you do this?
The objective is to reduce code review time by preventing changes that ESLint can address during development.
Card
Who/what does this impact?
Few existing LOCs were affected by this.
How did you test this?
Zero issues by running
pnpm run lint.